|
|
|
|
|
HI Mr. Jim Chen, Could you update your progress on this issue review ? Can you explain current status with AMLOGIC ? By the way, I asked Mr. Jacky Chiang to update Foxconn's progress every 5:00 PM in your time. I should update our review result and action plan to SKB everyday. Please keep in mind. |
|
|
Hi, Mr. Yoon, Mr. YK and AML has digged this issue for a while. I can only learn their knowhow from Jira, It's hard for me to have something new to update. Since the solution currently is to "repair" when the issue happen, I'll try to find "why" the issue happen. However with the probability that is 0.1~0.3%，"repair" way is much more efficient. The plan is to make an auto test environment, to see if there's any clue on the console when issue happen, and will also be usable for verifying the solutions from AML. Here's the items need to be solved: 1. study the linux based burning tool. (ok) 2. linux based burning tool not stable. 3. make special version of A9/A10 that will (ota/burn) to each other 4. OTA should through network since USB port is occupied by A-A cable |
|
|
Hi Jim Chen, Do you have any experience to update OS version for your any product ? If you have, please share your experience to us. |
|
|
Hi Mr. Yoon, Most update are just flash(nand/nor/emmc) partition update with check algorithm. The special part of this issue is that we use 2-steps update, that is: 1. update bootloader, recovery (maybe more) partition, and reboot again to enter "new recovery" 2. new recovery will handle the rest of the partition update. my rough guess is, reboot of step1 is too fast so that some data doesn't sync well in emmc so after reboot we get into trouble with those check algorithm however there's no evidence for above, and If we add some delay before step1 reboot, we need an auto test environment to verify it. |
|
|
to simplify the auto test environment, here's the changed plan 1. make 2 special Android10 FW 2. force enable the 2-steps update 3. assign different USB FW upgrade path 4. after bootup, automatically reboot into recovery to update. and here update some of my study, please check with attached the red part is step1, we can see 3 partitions are update: bootloader.img dt.img recovery.img if we want to dealy before reboot, it could put in set_bootloader_env it's a c-code func that we can add some flush() and sleep() updater-script.PNG (51,208 bytes) |
|
|
Hi Jim Chen This issue has been resolved. Thank you for your support. YK.Jung |
- yk.jung ( (ALTech) Younkwang Jung ) developer
